Skip to main content
Historic England

Conservation area

There is a problem

  • entry-date column must be in YYYY-MM-DD format

Buckland Dinham

reference
1791
name
Buckland Dinham
designation-date
1989-01-01
document-url
documentation-url
geometry
MULTIPOLYGON (((-2.353081 51.261303,-2.353118 51.261230,-2.353192 51.261044,-2.353311 51.261001,-2.353610 51.261028,-2.353654 51.260901,-2.353756 51.260540,-2.353899 51.260248,-2.354013 51.260121,-2.354272 51.259877,-2.354638 51.259885,-2.355018 51.259869,-2.355672 51.259879,-2.355678 51.260022,-2.355928 51.260030,-2.355924 51.260095,-2.356172 51.260110,-2.356181 51.259999,-2.356589 51.260009,-2.356650 51.260000,-2.356653 51.259991,-2.356888 51.260011,-2.356974 51.259809,-2.356989 51.259747,-2.356979 51.259557,-2.356997 51.259533,-2.357026 51.259517,-2.357132 51.258796,-2.357139 51.258622,-2.357175 51.258603,-2.357176 51.258565,-2.357160 51.258552,-2.357166 51.258512,-2.357173 51.258490,-2.357216 51.258471,-2.357229 51.258414,-2.357192 51.258388,-2.357212 51.258326,-2.357255 51.258336,-2.357284 51.258276,-2.357250 51.258252,-2.357526 51.257806,-2.357553 51.257789,-2.357554 51.257753,-2.357741 51.257466,-2.357746 51.257418,-2.357900 51.257194,-2.358063 51.256884,-2.358119 51.256717,-2.358178 51.256442,-2.358171 51.256366,-2.358151 51.256286,-2.358096 51.256150,-2.358179 51.256108,-2.358190 51.256051,-2.358043 51.256027,-2.357309 51.255870,-2.357049 51.255800,-2.356968 51.255762,-2.356988 51.255689,-2.356994 51.255572,-2.357031 51.255454,-2.357012 51.255302,-2.357012 51.255218,-2.356414 51.255211,-2.356063 51.255196,-2.356063 51.255139,-2.355521 51.255168,-2.354833 51.255267,-2.354794 51.255188,-2.354716 51.254954,-2.354368 51.255071,-2.354160 51.255107,-2.353874 51.255143,-2.353911 51.255219,-2.353819 51.255227,-2.352825 51.255414,-2.352464 51.255617,-2.352370 51.255683,-2.352270 51.255736,-2.352169 51.255663,-2.352011 51.255566,-2.351894 51.255460,-2.351855 51.255438,-2.351743 51.255406,-2.351612 51.255492,-2.351511 51.255537,-2.351447 51.255552,-2.351403 51.255582,-2.351370 51.255590,-2.351282 51.255668,-2.351272 51.255682,-2.351273 51.255704,-2.351244 51.255787,-2.351134 51.255898,-2.351095 51.255928,-2.351030 51.256038,-2.351020 51.256074,-2.351016 51.256197,-2.351039 51.256286,-2.351025 51.256315,-2.350980 51.256332,-2.350626 51.256293,-2.350495 51.256287,-2.350385 51.256296,-2.350255 51.256331,-2.350243 51.256336,-2.350292 51.256326,-2.350206 51.256351,-2.350124 51.256389,-2.350066 51.256448,-2.349855 51.256778,-2.349593 51.257017,-2.349541 51.257077,-2.349409 51.257176,-2.348904 51.257447,-2.348831 51.257512,-2.348758 51.257600,-2.348687 51.257716,-2.349419 51.258069,-2.349372 51.258084,-2.349262 51.258188,-2.349241 51.258311,-2.349213 51.258391,-2.349193 51.258417,-2.349094 51.258497,-2.348980 51.258614,-2.348900 51.258634,-2.348878 51.258650,-2.348868 51.258671,-2.348869 51.258697,-2.348929 51.258813,-2.348933 51.258846,-2.348921 51.258912,-2.348890 51.258981,-2.348857 51.258992,-2.348841 51.258989,-2.348732 51.258936,-2.348676 51.258936,-2.348652 51.258947,-2.348610 51.259000,-2.348343 51.259403,-2.348280 51.259519,-2.349338 51.259712,-2.350147 51.259871,-2.350256 51.259911,-2.350296 51.259934,-2.350326 51.259967,-2.350410 51.260028,-2.350475 51.260053,-2.350784 51.260129,-2.351330 51.260238,-2.351262 51.260522,-2.352047 51.260607,-2.352037 51.260648,-2.352186 51.260663,-2.352101 51.260778,-2.352008 51.260880,-2.351984 51.261142,-2.351902 51.261302,-2.352238 51.261369,-2.352422 51.261397,-2.352567 51.261359,-2.352790 51.261276,-2.353081 51.261303)))
point
POINT (-2.353464 51.257918)
notes
organisation
entry-date

entry-date must be a real date

2025-04-01
start-date
1989-01-01
end-date

How to fix this issue

Your dataset is missing the entry-date column.

The Conservation area guidance explains how to fix the issue:

entry-date

The date the record was last updated.

If the entity has never been updated, enter the same date as start-date.

Write in YYYY-MM-DD format.

Example:

2022-12-20

With dates, some data is better than no data, so:

  • 2022 is fine
  • 2022-12 is better
  • 2022-12-20 is brilliant

How to improve Historic England’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL